Skip to content

Conversation

@maxy-shpfy
Copy link
Collaborator

@maxy-shpfy maxy-shpfy commented Jan 10, 2026

Description

Closes https://github.com/Shopify/oasis-frontend/issues/414

Added support for displaying task arguments in the IO Node and Input Value Editor. This enhancement allows users to see when a pipeline input has been overridden with an argument value, clearly indicating when a value is not the default.

Type of Change

  • New feature
  • Improvement

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Test Instructions

Screen Recording 2026-01-09 at 4.59.02 PM.mov (uploaded via Graphite)

  1. Create and run a pipeline with various input arguments - you can use http://localhost:8000/docs#/pipelineRuns/create_api_pipeline_runs__post (or replace origin with proper host/port)
  2. Verify that the IO nodes display the argument values instead of defaults
  3. Confirm that the Input Value Editor shows the argument value and correctly indicates when a value is not the default

Additional Comments

This change extracts the getArgumentValue function into a separate utility file for reuse and adds conditional rendering of the "Use as default" indicator based on whether the current value is an argument override.

Comment on lines +119 to +131
isDefault ? (
<InlineStack gap="1" className="ml-2">
<Icon
name="SquareCheckBig"
size="sm"
className="text-muted-foreground"
/>

<Paragraph tone="subdued" size="xs">
Use as default
</Paragraph>
</InlineStack>
) : null
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A little rusty after the break but does isDefault && (<Component />) work instead of a full ternary?

placeholder={placeholder}
disabled={disabled}
inputName={input.name}
isDefault={!argumentValue || argumentValue === defaultInputValue}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For tidiness maybe extract this into a variable.

Copy link
Collaborator

@camielvs camielvs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if just the "Use as Default" checkmark is sufficient as a differentiator. It is rather subtle. For values that come from external sources maybe we need a specific icon/info text for that? e.g. "Value provided externally" or something like that

@maxy-shpfy maxy-shpfy changed the base branch from 01-09-feat_display_taskspec_arguments_values_in_run_view to graphite-base/1612 January 15, 2026 02:48
@maxy-shpfy maxy-shpfy force-pushed the 01-09-feat_display_arguments_values_in_input_nodes_in_run_view branch from e19e404 to 3612180 Compare January 15, 2026 02:51
@graphite-app graphite-app bot changed the base branch from graphite-base/1612 to master January 15, 2026 02:51
@maxy-shpfy maxy-shpfy force-pushed the 01-09-feat_display_arguments_values_in_input_nodes_in_run_view branch from 3612180 to e662951 Compare January 15, 2026 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants